Appendix A
(normative)
Uppsala University, Sweden
Servers | Comments | ||||||
---|---|---|---|---|---|---|---|
One | Two | Three | Four | Five | |||
1. | Event creation. | ||||||
P | P | P | P | 1.1. | Create new single-instance meeting titled “Meeting 1.1” with the location “Durham”. | ||
P | P | P | P | 1.2. | Create new meeting titled “Meeting 1.2” recurring every Monday from 10:00 AM to 11:00 AM for 4 weeks. | ||
P* | P | P** | P | 1.3. | Create new single-instance meeting titled “Meeting 1.3” with 2 other attendees. | * & ** No cuaddr to test with, used CalDAV1 & CalDAV2, got ‘?’. Could use iMIP, and update status though email. NB: for iMip, e-mail address of sender/organizer must match cuaddr (problem w/ many e-mail addresses configured on either client) | |
P | P | P | P | 1.4. | Create new single-instance meeting titled “Meeting 1.4” with an alarm set to trigger 15 minutes prior to the schedule time of the meeting. | ||
2. | Event modification | ||||||
P | P | P | P | 2.1. | Modify the title of meeting “Meeting 1.1” to “Meeting 1.1bis”. | ||
P | P | P | P | 2.2. | Modify the location of the meeting “Meeting 1.1bis” to “Seattle bis”. | ||
P | P | P | P | 2.3. | Reschedule meeting “Meeting 1.1bis” to the next day. | ||
P | P | P | P | 2.4. | Add an attendee to “Meeting 1.1bis”. | ||
P | P | P | P | 2.5. | Add an alarm to “Meeting 1.1bis”. | ||
P | P | P | P | 2.6. | Modify the title of the 1st instance of the recurring meeting created in 1.2. | ||
P | P** | P | P | 2.7. | Modify the participation status of the 1st attendee in meeting 1.3 to | ** iMIP broken on test server. | |
P | P | P | P | 2.8. | Cancel the 4th instance of the recurring meeting created in 1.2. | ||
P | P | P | P | 2.9. | One client changes “Meeting 1.1bis” to a different time, second client ‘refreshes’ its display to see the modification. | ||
4. | Event deletion | ||||||
P | P | P | P | 4.1. | Delete a single non-recurring meeting. | ||
P | P | P | P | 4.2. | Delete a single recurring meeting with no overridden instances. | ||
P | P | P | P | 4.3. | Delete a single recurring meeting with overridden instances. | Deleting all instances, even those that are already deleted. | |
P | P | P | P* | 4.4. | Delete a non-overridden instance of a recurring meeting. | The FIRST time (only) a single but repeated instance is deleted, it comes back! | |
N | N | N | N | 4.5. | Delete an overridden instance of a recurring meeting. | ||
5. | Access Control | ||||||
N | N | N | N | 5.1. | View access control details on current user’s main calendar. | ||
N | N | N | N | 5.2. | Change access control details on current user’s main calendar to add another user with read-only access. Verify that other user can view the calendar but not change it. | ||
N | N | N | N | 5.3. | Change access control details on current user’s main calendar to add another user with read-write access. Verify that other user can view the calendar and change it. Verify that changes done by one user are seen by the other. | ||
N | N | N | N | 5.4. | Remove another user’s access to the current user’s main calendar and verify they can no longer access the calendar. | ||
6 | Calendar Management | ||||||
N | N | N | N | 6.1 | Browse the list of calendars on the server, including the current user’s personal calendars. | ||
P* | P | P | P | 6.2 | Create a new calendar in the current user’s personal calendar space. | * Can create calendar, but it not writable. Will do after restart of client. Bug fixed in server! | |
N | N | N | N | 6.3 | Create a regular collection in the current user’s personal calendar space. | ||
N | N | N | N | 6.4 | Create a new calendar inside the collection created in 6.3. | ||
P | P | P | P | 6.5 | Delete the calendar created in 6.2. | ||
N | N | N | N | 6.6 | Delete the collection created in 6.3. |